Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updating Microsoft Defender for Endpoints to use new initiative #1639

Merged
merged 9 commits into from
May 21, 2024

Conversation

Springstone
Copy link
Member

@Springstone Springstone commented May 14, 2024

Overview/Summary

This pull request introduces significant changes to the eslzArm/eslzArm.json and docs/wiki/Whats-new.md files. The main changes are the deprecation of certain policies and the introduction of new ones, as well as the addition of a new initiative for Microsoft Defender for Endpoints. In addition, there are some adjustments in the eslzArm/eslzArm.json file to accommodate these new policies and initiatives.

Policy changes:

  • docs/wiki/Whats-new.md: Deprecated the custom policy "Storage Account set to minimum TLS and Secure transfer should be enabled" and replaced it with two built-in policies. Also deprecated the "Deploy-EncryptTransit" initiative and superseded it with "Deploy-EncryptTransit_20240509". Added a new custom policy "Deploy-Private-DNS-Generic" and a new initiative for Microsoft Defender for Endpoints.

Adjustments in eslzArm/eslzArm.json:

  • Added the "mdEnpointsAMAPolicyInitiative" and "mdEndpointsAMADeploymentName" variables. [1] [2]
  • Added a new block of code to assign the new Microsoft Defender for Endpoints policy initiative to the intermediate root management group if the condition is true.

Addition of a new policy assignment:

Azure Public

Deploy To Azure

As part of this Pull Request I have

  • Checked for duplicate Pull Requests
  • Associated it with relevant issues, for tracking and closure.
  • Ensured my code/branch is up-to-date with the latest changes in the main branch
  • Performed testing and provided evidence.
  • Ensured contribution guidance is followed.
  • Updated relevant and associated documentation.
  • Updated the "What's New?" wiki page (located: /docs/wiki/whats-new.md)

@Springstone Springstone requested a review from a team as a code owner May 14, 2024 10:54
@Springstone Springstone added Area: Policy 📝 Issues / PR's related to Policy Status: Do Not Merge ⛔ Do not merge PRs with this label attached as they are not ready etc. labels May 14, 2024
@Springstone Springstone removed the Status: Do Not Merge ⛔ Do not merge PRs with this label attached as they are not ready etc. label May 14, 2024
@Springstone Springstone added the PR: Safe to test 🧪 PRs can run more advanced tests that may deploy or access environments label May 17, 2024
@Springstone Springstone reopened this May 17, 2024
@jtracey93 jtracey93 merged commit 97022e9 into policy-refresh-q3fy24 May 21, 2024
3 of 5 checks passed
@jtracey93 jtracey93 deleted the MDE branch May 21, 2024 10:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Policy 📝 Issues / PR's related to Policy Needs: Author Feedback PR: Safe to test 🧪 PRs can run more advanced tests that may deploy or access environments
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants